Component references
Components can be created once and used in process steps across multiple processes. This modular design simplifies maintenance because configuration changes can be made once and then instantly applied everywhere the component is referenced. Each time a component uses or is used by another component, a reference (or in other words, a direct relationship) is formed between them.
Types of component references
Depending on the type of component you are using, it can create a dependent or independent reference to other components it uses or is used by. Knowing the difference between both reference types can help you understand how a component needs to be packaged and deployed.
-
Dependent references - Most component references are dependent references, which means that the component is automatically included when the process is packaged; they don't need to be packaged and deployed separately.
-
Independent references - They are less common and are defined as components that must be packaged and deployed independently. Independent references allow for greater flexibility in deployment versioning. Independent references include relationships between processes and:
-
API Service components
-
Flow Service components
-
Process Route components
-
Processing Group components
-
Although API Proxies, Certificates, and Custom Libraries can be independently deployed, they do not have references to or from other components and therefore are not classified as either dependent or independent. For more information about packaging and deployment, refer to the Deployment section.
Exploring component references
You can use the Show Where Used filter in the user interface or the Component Reference API object to view dependent or independent references between components.
- Use the Show Where Used filter to filter out the parent processes or components where a common child component is used.
- Use the Component Reference object to find all the parent components that use a common child component or, conversely, to find all the child components that are used in a given parent component. Additionally, you can use this object to query for components by dependent or independent reference type.
References and deleted components
Once you delete a component from the Component Explorer, the deleted component is no longer displayed in the Component Explorer and is not returned in the list of Show Where Used filter results.
Though references are removed from the deleted component, the component will still display in the process canvas until it is either replaced with an active component or is removed from the process. The process canvas will show red text for any deleted component that requires cleanup.
